This repository has been archived by the owner on Nov 9, 2023. It is now read-only.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR does 3 things:
qiime.filter.filter_mapping_file
behaves to match the documentation.--output_mapping_fp
infilter_samples_from_otu_table.py
: now writes a subsetted mapping file that retains all the metadata columns of the original passed mapping file regardless of their uniqueness status.filter_samples_from_otu_table.py
for the--output_mapping_fp
I believe change 2 is good because: we are not exposing the control of whether or not unique metadata columns are written in the script (we don't mention it in the documentation either) and so it is very startling to see that data disappear when you use the
--output_mapping_fp
option. In addition, its easy to remove columns in e.g. excel, whereas its annoying to have to add columns back in if you have output a reduced mapping file. Also, its useful to retain non-unique and totally unique columns with a reduced mapping file if you are e.g. trying to work with a new dataset and see what the values for a particular set of samples are.